fix: support "form_post" to be one of response modes in authorization server metadata validation#1046
Merged
pcarleton merged 3 commits intomodelcontextprotocol:mainfrom Jul 4, 2025
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add
form_posttoOAuthMetadta.response_modes_supportedarray.Motivation and Context
"form_post" is one of valid values - RFC 8414 OAuth 2.0 Authorization Server Metadata
Currently if authorization server metadata endpoint returns
response_mode_supportedthat containsform_post, the validation will fail:How Has This Been Tested?
Tested locally, ensure authorize goes to the authorization server that passed to simple auth server.
Breaking Changes
No.
Types of changes
Checklist
Additional context